Add gh enterprise early access program details with policy #751
Conversation
pages/training/gh-enterprise.md
Outdated
| Should the owner of a Github Organisation leave the University, the ownership of the organisation must be transferred to an eligible member of UoS or transferred under management of the UoS Enterprise Administration team if there are no eligible members and it is in the interests of the University to retain the organisation. Otherwise the organisation should be deleted along with its contents. | ||
|
|
||
| #### 1.3.4 Yearly Github Organisation Audit | ||
| A yearly audit is performed by the UoS Enterprise Administration team to ensure access and ownership is in compliance with the Eligibility criteria. Github Organisations no longer in use should be removed. The owner of the Github Organisation will work with the UoS Enterprise Administration to facilitate the process. |
There was a problem hiding this comment.
So if I generate a DOI with Zenodo/Figshare (which will admittedly capture a snapshot), I should expect that after the research project has ended the repo will be deleted (assuming org created for the project) along with any metadata/commit history not present in the Zenodo snapshot?
Likewise, many less RSE staff may link to GitHub repos in papers (as was the case one I reviewed at the weekend), if orgs and consequently repos are to be deleted, rather than merely marked inactive, this seems really bad.
I can see this being undesirable for many that currently have generic academic GH organisations which can be long-lived.
There was a problem hiding this comment.
If the repo has a DOI or historically relevant then they should definitely be kept for archival purposes. Thanks, I'll clarify this in the policy.
pages/training/gh-enterprise.md
Outdated
| ## 2. Communications | ||
| Various channels of communication are available: | ||
|
|
||
| - The [github-enterprise-announce](https://groups.google.com/a/sheffield.ac.uk/g/github-enterprise-announce-group) google group is used to announce service updates. Organisation owners and administrators are automatically enrolled in the group. |
There was a problem hiding this comment.
I may need to be added to this group, I already have an org that you created for me a few months ago.
Co-authored-by: Robert Chisholm <r.chisholm@sheffield.ac.uk>
|
Thanks @Robadob, some really good suggestions. I'll add/amend the policy. |
Co-authored-by: Robert Chisholm <r.chisholm@sheffield.ac.uk>
pages/training/gh-enterprise.md
Outdated
| type: text | ||
| --- | ||
|
|
||
| In collaboration with IT Services, the RSE team is providing limited early access to the University's Github Enterprise. This is to allow researchers and academics to get the full [benefits of Github Enterprise](https://docs.github.com/en/get-started/learning-about-github/githubs-plans) now while allowing us to obtain feedback which will be used to refine the service offering in the eventual university-wide rollout. |
There was a problem hiding this comment.
Perhaps link directly to the section on GitHub Enterprise.
| In collaboration with IT Services, the RSE team is providing limited early access to the University's Github Enterprise. This is to allow researchers and academics to get the full [benefits of Github Enterprise](https://docs.github.com/en/get-started/learning-about-github/githubs-plans) now while allowing us to obtain feedback which will be used to refine the service offering in the eventual university-wide rollout. | |
| In collaboration with IT Services, the RSE team is providing limited early access to the University's Github Enterprise. This is to allow researchers and academics to get the full [benefits of Github Enterprise](https://docs.github.com/en/get-started/learning-about-github/githubs-plans#github-enterprise) now while allowing us to obtain feedback which will be used to refine the service offering in the eventual university-wide rollout. |
|
Looks good and great to see this coming to fruition. One minor suggestion to make the link on benefits more direct. I'd also be inclined to hard-wrap long lines at a set number of characters. If #701 ever see's the light of day and is merged I think its set to 120 characters. Makes marginally easier diffing in the long term. |
|
Thanks @ns-rse, suggested changes added. |
No description provided.